home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19941221-19950208
/
000298_news@columbia.edu_Fri Jan 27 20:38:27 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA23816
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Fri, 27 Jan 1995 20:29:40 -0500
Received: by apakabar.cc.columbia.edu id AA26557
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 27 Jan 1995 20:29:39 -0500
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!sol.ctr.columbia.edu!spool.mu.edu!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!gatech!udel!news.mathworks.com!news.duke.edu!eff!news.umbc.edu!haven.umd.edu!purdue!mozo.cc.purdue.edu!news.physics.purdue.edu!london.physics.purdue.edu!korty
From: korty@london.physics.purdue.edu (Andrew J. Korty)
Subject: Re: File Transfers Fail Uploading but not Downloading!
Message-Id: <D33004.1Dp@physics.purdue.edu>
Sender: usenet@physics.purdue.edu (News Administration)
Organization: Physics Department, Purdue University
References: <D31EGK.Mo3@physics.purdue.edu> <3gb0hr$ki@apakabar.cc.columbia.edu>
Date: Fri, 27 Jan 1995 20:38:27 GMT
Lines: 40
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3gb0hr$ki@apakabar.cc.columbia.edu>,
Frank da Cruz <fdc@watsun.cc.columbia.edu> wrote:
>Yours are the classic symptoms of big buffers in the downstream direction,
>tiny buffers in the upstream direction. A common configuration, based on
>the assumption that when one makes a dialup connection, the only upstream
>traffic will be keystrokes (at most, 10 per second), but the downstream
>traffic will be voluminous (the responses to your commands).
>
>Where are these "buffers"? Probably in the terminal server. And in your
>case maybe we also have something going on with the modems. Maybe your
>DOV modems allocate higher bandwidth upstream than down.
>
>To cope with this situation, you can sometimes reconfigure the
>communications equipment to be more symmetrical. This requires digging
>through the technical manuals for the devices involved.
... and having access to that communications equipment. I doubt PUCC
would be to keen on such an extended level of customer service.
>But in any case, it is ESSENTIAL to institute the most effective possible
>means of flow control at EVERY juncture along the communication path:
>between your PC and the modem, between the answering modem and the
>terminal server, and so on. This should be "hardware" (RTS/CTS) flow
>control if it is available. In-band "software" flow control methods such
>as Xon/Xoff do not work nearly as well. Unfortunately RTS/CTS is not
>always available. For example, one popular terminal server model supports
>RTS/CTS only in one direction (the downloading one, on the aforementioned
>assumption) so uploads through these devices often run into trouble.
Well, I was using RTS/CTS between my PC and the modem, and no flow
control between the machine and the terminal server. I've tried
changing these with no success. I can't figure out what the modem
pool uses to communicate with the terminal server, and I don't think I
could change it if I needed to.
So, I guess I'm just hosed, unless other people start complaining
about this as well ...
Andy